…26-04-28) (#80)

Three structural fixes for the PR #23 mise+bun-1.3.13 502 transient
class, addressing Aaron 2026-04-28 directives:

  "is there not a way to fix this?" (don't default to rerun)
  "we want to use stock and we better not be using that old
   version of ubuntu"
  "can you cache and retry?"
  "we want to make sure dev seutp and build machine setup are as
   close to the same a possible"
  "why not cache the whole install/setup"

1. **Comprehensive install cache** on lint-shell, lint-workflows,
   lint-markdown jobs (previously uncached). Caches everything
   tools/setup/install.sh writes:
     ~/.local/bin/mise (the mise binary)
     ~/.local/share/mise (mise runtimes — bun/dotnet/python/uv/java)
     ~/.cache/mise (mise download cache)
     ~/.dotnet/tools (dotnet global tools)
     ~/.elan (Lean toolchain)
     ~/.config/zeta (managed shellenv)
     tools/tla, tools/alloy (verifier jars)
   Cache key hashes BOTH .mise.toml AND tools/setup/** so install
   logic changes invalidate cache → vanilla install path gets
   re-tested whenever discipline changes.

2. **Retry layer** on the install step (CI-only — dev runs stay
   interactive). Three attempts with 10s/30s backoff. Mise's
   internal 3-attempt retry was exhausted on PR #23's bun download;
   wrapping at the install.sh layer catches the case where mise
   itself gives up. Same shape across all 3 lint jobs.

3. **Ubuntu 24.04 bump** on every workflow that pinned ubuntu-22.04
   (gate.yml lint jobs ×6, resume-diff.yml, scorecard.yml,
   memory-index-duplicate-lint.yml, budget-snapshot-cadence.yml).
   ubuntu-latest = ubuntu-24.04 since Jan 2025 per Otto-247 WebSearch
   verification; 22.04 is now LTS-2 stale. Stays on stock GitHub-
   hosted runner image (no custom pre-installed bun) per Aaron's
   "we want to use stock" + "vanilla ubuntu so we test do our install
   scripts work on vanalla and deve machines."

Dev↔CI parity: install.sh runs on both surfaces; cache restores
state similar to a dev's already-bootstrapped local env; cache key
on tools/setup/** + .mise.toml matches what a dev's environment
depends on. install.sh stays idempotent so cache hit = fast no-op,
cache miss = full vanilla install (which is the install-script
validation Aaron wants).

Composes with PR #75 curl_fetch helper (downstream curl retries),
PR #76 + #79 markdownlint carve-outs (verbatim ferry preservation),
Otto-247 version-currency, Otto-235 4-shell portability, Otto-341
mechanism-over-vigilance, and `feedback_structural_fix_beats_process_discipline_velocity_multiplier_aaron_2026_04_28.md`.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

* ci: comprehensive install cache + retry + ubuntu-24.04 bump (Aaron 2026-04-28)

Three structural fixes for the PR #23 mise+bun-1.3.13 502 transient
class, addressing Aaron 2026-04-28 directives:

  "is there not a way to fix this?" (don't default to rerun)
  "we want to use stock and we better not be using that old
   version of ubuntu"
  "can you cache and retry?"
  "we want to make sure dev seutp and build machine setup are as
   close to the same a possible"
  "why not cache the whole install/setup"

1. **Comprehensive install cache** on lint-shell, lint-workflows,
   lint-markdown jobs (previously uncached). Caches everything
   tools/setup/install.sh writes:
     ~/.local/bin/mise (the mise binary)
     ~/.local/share/mise (mise runtimes — bun/dotnet/python/uv/java)
     ~/.cache/mise (mise download cache)
     ~/.dotnet/tools (dotnet global tools)
     ~/.elan (Lean toolchain)
     ~/.config/zeta (managed shellenv)
     tools/tla, tools/alloy (verifier jars)
   Cache key hashes BOTH .mise.toml AND tools/setup/** so install
   logic changes invalidate cache → vanilla install path gets
   re-tested whenever discipline changes.

2. **Retry layer** on the install step (CI-only — dev runs stay
   interactive). Three attempts with 10s/30s backoff. Mise's
   internal 3-attempt retry was exhausted on PR #23's bun download;
   wrapping at the install.sh layer catches the case where mise
   itself gives up. Same shape across all 3 lint jobs.

3. **Ubuntu 24.04 bump** on every workflow that pinned ubuntu-22.04
   (gate.yml lint jobs ×6, resume-diff.yml, scorecard.yml,
   memory-index-duplicate-lint.yml, budget-snapshot-cadence.yml).
   ubuntu-latest = ubuntu-24.04 since Jan 2025 per Otto-247 WebSearch
   verification; 22.04 is now LTS-2 stale. Stays on stock GitHub-
   hosted runner image (no custom pre-installed bun) per Aaron's
   "we want to use stock" + "vanilla ubuntu so we test do our install
   scripts work on vanalla and deve machines."

Dev↔CI parity: install.sh runs on both surfaces; cache restores
state similar to a dev's already-bootstrapped local env; cache key
on tools/setup/** + .mise.toml matches what a dev's environment
depends on. install.sh stays idempotent so cache hit = fast no-op,
cache miss = full vanilla install (which is the install-script
validation Aaron wants).

Composes with PR #75 curl_fetch helper (downstream curl retries),
PR #76 + #79 markdownlint carve-outs (verbatim ferry preservation),
Otto-247 version-currency, Otto-235 4-shell portability, Otto-341
mechanism-over-vigilance, and `feedback_structural_fix_beats_process_discipline_velocity_multiplier_aaron_2026_04_28.md`.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* ci: bump install retry from 3 to 5 attempts with 10s/30s/60s/120s backoff (Aaron 2026-04-28)

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…+ retry 3→5 (Aaron 2026-04-28) (Lucent-Financial-Group#700)

* ci: comprehensive install cache + retry + ubuntu-24.04 bump (Aaron 2026-04-28) (#80)

Three structural fixes for the PR #23 mise+bun-1.3.13 502 transient
class, addressing Aaron 2026-04-28 directives:

  "is there not a way to fix this?" (don't default to rerun)
  "we want to use stock and we better not be using that old
   version of ubuntu"
  "can you cache and retry?"
  "we want to make sure dev seutp and build machine setup are as
   close to the same a possible"
  "why not cache the whole install/setup"

1. **Comprehensive install cache** on lint-shell, lint-workflows,
   lint-markdown jobs (previously uncached). Caches everything
   tools/setup/install.sh writes:
     ~/.local/bin/mise (the mise binary)
     ~/.local/share/mise (mise runtimes — bun/dotnet/python/uv/java)
     ~/.cache/mise (mise download cache)
     ~/.dotnet/tools (dotnet global tools)
     ~/.elan (Lean toolchain)
     ~/.config/zeta (managed shellenv)
     tools/tla, tools/alloy (verifier jars)
   Cache key hashes BOTH .mise.toml AND tools/setup/** so install
   logic changes invalidate cache → vanilla install path gets
   re-tested whenever discipline changes.

2. **Retry layer** on the install step (CI-only — dev runs stay
   interactive). Three attempts with 10s/30s backoff. Mise's
   internal 3-attempt retry was exhausted on PR #23's bun download;
   wrapping at the install.sh layer catches the case where mise
   itself gives up. Same shape across all 3 lint jobs.

3. **Ubuntu 24.04 bump** on every workflow that pinned ubuntu-22.04
   (gate.yml lint jobs ×6, resume-diff.yml, scorecard.yml,
   memory-index-duplicate-lint.yml, budget-snapshot-cadence.yml).
   ubuntu-latest = ubuntu-24.04 since Jan 2025 per Otto-247 WebSearch
   verification; 22.04 is now LTS-2 stale. Stays on stock GitHub-
   hosted runner image (no custom pre-installed bun) per Aaron's
   "we want to use stock" + "vanilla ubuntu so we test do our install
   scripts work on vanalla and deve machines."

Dev↔CI parity: install.sh runs on both surfaces; cache restores
state similar to a dev's already-bootstrapped local env; cache key
on tools/setup/** + .mise.toml matches what a dev's environment
depends on. install.sh stays idempotent so cache hit = fast no-op,
cache miss = full vanilla install (which is the install-script
validation Aaron wants).

Composes with PR #75 curl_fetch helper (downstream curl retries),
PR #76 + #79 markdownlint carve-outs (verbatim ferry preservation),
Otto-247 version-currency, Otto-235 4-shell portability, Otto-341
mechanism-over-vigilance, and `feedback_structural_fix_beats_process_discipline_velocity_multiplier_aaron_2026_04_28.md`.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

* ci: bump install retry from 3 to 5 attempts (Aaron 2026-04-28) (#81)

* ci: comprehensive install cache + retry + ubuntu-24.04 bump (Aaron 2026-04-28)

Three structural fixes for the PR #23 mise+bun-1.3.13 502 transient
class, addressing Aaron 2026-04-28 directives:

  "is there not a way to fix this?" (don't default to rerun)
  "we want to use stock and we better not be using that old
   version of ubuntu"
  "can you cache and retry?"
  "we want to make sure dev seutp and build machine setup are as
   close to the same a possible"
  "why not cache the whole install/setup"

1. **Comprehensive install cache** on lint-shell, lint-workflows,
   lint-markdown jobs (previously uncached). Caches everything
   tools/setup/install.sh writes:
     ~/.local/bin/mise (the mise binary)
     ~/.local/share/mise (mise runtimes — bun/dotnet/python/uv/java)
     ~/.cache/mise (mise download cache)
     ~/.dotnet/tools (dotnet global tools)
     ~/.elan (Lean toolchain)
     ~/.config/zeta (managed shellenv)
     tools/tla, tools/alloy (verifier jars)
   Cache key hashes BOTH .mise.toml AND tools/setup/** so install
   logic changes invalidate cache → vanilla install path gets
   re-tested whenever discipline changes.

2. **Retry layer** on the install step (CI-only — dev runs stay
   interactive). Three attempts with 10s/30s backoff. Mise's
   internal 3-attempt retry was exhausted on PR #23's bun download;
   wrapping at the install.sh layer catches the case where mise
   itself gives up. Same shape across all 3 lint jobs.

3. **Ubuntu 24.04 bump** on every workflow that pinned ubuntu-22.04
   (gate.yml lint jobs ×6, resume-diff.yml, scorecard.yml,
   memory-index-duplicate-lint.yml, budget-snapshot-cadence.yml).
   ubuntu-latest = ubuntu-24.04 since Jan 2025 per Otto-247 WebSearch
   verification; 22.04 is now LTS-2 stale. Stays on stock GitHub-
   hosted runner image (no custom pre-installed bun) per Aaron's
   "we want to use stock" + "vanilla ubuntu so we test do our install
   scripts work on vanalla and deve machines."

Dev↔CI parity: install.sh runs on both surfaces; cache restores
state similar to a dev's already-bootstrapped local env; cache key
on tools/setup/** + .mise.toml matches what a dev's environment
depends on. install.sh stays idempotent so cache hit = fast no-op,
cache miss = full vanilla install (which is the install-script
validation Aaron wants).

Composes with PR #75 curl_fetch helper (downstream curl retries),
PR #76 + #79 markdownlint carve-outs (verbatim ferry preservation),
Otto-247 version-currency, Otto-235 4-shell portability, Otto-341
mechanism-over-vigilance, and `feedback_structural_fix_beats_process_discipline_velocity_multiplier_aaron_2026_04_28.md`.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* ci: bump install retry from 3 to 5 attempts with 10s/30s/60s/120s backoff (Aaron 2026-04-28)

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

* ci: address PR Lucent-Financial-Group#700 Copilot threads + Otto-357 no-directives correction (5 fixes)

Five fixes in gate.yml addressing Copilot review threads + the human
maintainer's reinforcement of Otto-357 (no-directives framing):

## 1. Otto-357 no-directives framing (4 spots)

The human maintainer's catch: "the only directive is there is no
directive". Per Otto-357 + the no-directives rule in CLAUDE.md,
framing the maintainer's input as "directive" makes Otto a follower-
of-orders rather than an accountable autonomous peer. Replaced 4
occurrences of "the human maintainer's directive" / "Aaron 2026-04-28
directive" with "the human maintainer's input" / "the human
maintainer's 2026-04-28 input" / "dev-CI parity input" / etc.

## 2. Aaron→role-ref attribution (Otto-279 thread)

Per Otto-279 / the named-agent attribution rule, current-state
surfaces (workflows count) use role-refs ("the human maintainer")
not first-name attribution. Converted in the comments I introduced
or just edited; pre-existing Aaron-named comments left as-is for
scope hygiene.

## 3. Comprehensive install cache: drop tools/tla + tools/alloy

The cache key only hashed `.mise.toml + tools/setup/** + global.json`,
but the cache PATHS included `tools/tla` and `tools/alloy` — which
contain tracked source (e.g., `tools/alloy/AlloyRunner.java`,
first-party Java) AND are already cached by the dedicated "Cache
verifier jars (TLC + Alloy)" step earlier in the workflow. Caching
them in the comprehensive cache caused (a) double-cache races and
(b) cache-hit-but-stale on tracked-source edits (the cache key
wouldn't bust). Drop those paths; rely on the dedicated verifier-
jars cache for them.

## 4. Typo cleanup in directive-quote comments

"dev seutp" → "dev setup", "as close to the same a possible" →
"as close to the same as possible". Tension with verbatim-quote
substrate resolved by paraphrasing in the comment (the quoted
form is preserved in memory files; workflow comments are
current-state, prefer readable).

## 5. PR description over-claim — Setup Python step

The PR description claimed "Setup Python + Install Semgrep
(lint job)". Investigation showed the lint (semgrep) job uses
the install.sh-based pattern (no actions/setup-python) per the
host-portability invariant. The Setup Python addition from
AceHack #80 did NOT survive the cherry-pick because LFG-side
already moved to install.sh-based semgrep. PR description will
be corrected separately. The cache + retry are the real
substantive forward-sync content.

Retry-wrapper duplication suggestion (Copilot thread #3) noted
as a follow-up improvement candidate in-comment; not addressed
in this PR to keep scope tight.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>